Secure medication transport

ABSTRACT

A smart carrier has a housing comprising one or more docking locations configured to accept a secure receptacle, a wireless interface module disposed within the housing, and a processor disposed within the housing and operatively coupled to the one or more docking locations and the wireless interface module. The processor is configured to communicate with an external device through the wireless interface module and with a secure receptacle that is mated with one of the one or more docking locations. The smart carrier also has a battery disposed within the housing and configured to provide all operational power to the processor, the wireless interface module, and the one or more docking locations.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation patent application of patentapplication Ser. No. 15/432,862, filed on Feb. 14, 2017, which issued onJun. 11, 2019, as U.S. Pat. No. 10,318,713 entitled “SECURE MEDICATIONTRANSPORT,” which is related to and claims priority as a divisionalapplication of, application number Ser. No. 13/931,623, filed on Jun.28, 2013, which issued on Mar. 21, 2017, as U.S. Pat. No. 9,600,634entitled “SECURE MEDICATION TRANSPORT,” by Gary Bell, et-al. thecontents of which are hereby incorporated by reference in theirentirety, for all purposes.

BACKGROUND Field

The present disclosure generally relates to the transport of medicationsand, in particular, transfer of medications from a pharmacy to adispensing system.

Description of the Related Art

Patients are routinely prescribed a number of medications while in ahospital. Many hospitals utilize automated dispensing machines (ADMs) tosecurely store and dispense medications at sites, for example a nursingstation, that are remote from the pharmacy. While certain medicationsare stocked in the ADMs, it is necessary to replenish the stock ofmedications on a regular basis. In addition, as most ADMs do not havethe capacity to store all possible medications, a doctor may prescribe amedication that is not currently stocked in the local ADM and thepharmacy must send this medication to the ADM. Thus, there is a regulartransfer of medications from the pharmacy to multiple ADMs within thehospital or, in certain circumstances, to ADMs located in otherhospitals.

One method of transferring medications from the pharmacy to an ADM isdisclosed in U.S. Pat. No. 6,116,461 to Broadfield et al (hereinafter“the '461 patent”), which is incorporated herein in its entirety. The'461 patent discloses a receptacle with a lid that is held in a closedposition, thereby securing the contents of the receptacle, by aninternal latch controlled by an internal processor. When the receptacleis docked with a suitable receiving station, such as an ADM, theinternal processor is placed in communication with a processor in thereceiving station that is further linked to a central data systemcontaining information about medications. The processor of the receivingstation may send commands to the internal processor of the receptacle toactivate the latch, thereby allowing the lib to be opened. Medicationscan be transferred from the pharmacy to an ADM by docking a receptaclewith a “refill station” in the pharmacy. The '461 patent discloses aprocess in which the pharmacist or other operator scans a barcodeassociated with a medication, enters information such as a quantity andexpiration date, prints a label that may include medication informationin text or barcode form, places the medications in a receptacle andattaches the label to the receptacle, closes the lib, and removes thereceptacle from the refill station. The filled receptacle is then placedin a tote and transported to the ADM, the ADM is opened, and thereceptacle is docked with the ADM, thereby making the medicationavailable for dispensing from the ADM. One aspect of this system is thatthe receptacle can be opened only at fixed stations such as a fillingstation in the pharmacy or the ADM at the nurses' station.

Another conventional method of transferring medications is a manualprocess wherein medications are placed loose or in plastic bags in totesalong with routing sheets. Although most hospitals are takingprecautions to separate look-alike/sound-alike medications in compliancewith National Patient Safety Goals, there is still opportunity for erroras there are thousands of doses of medications available. During thecheck process, the picked medications are reviewed by scanning the labelon the bag and displaying information related to the contents of the bagon a screen for the checker to approve. These medications are collectedin totes that are then placed on a mobile cart for transport to the ADM.There is a risk, however, that a tote could be placed directly on thecart and thereby removing medications from the pharmacy without beingchecked. Furthermore, the medications have the potential to be separatedfrom their routing sheets during handling.

SUMMARY

It is advantageous to provide a mobile carrier that provides power and acommunication link to secure receptacles such that the securereceptacles may be filled, checked, and operated at locations other thanfixed filling and dispensing systems.

In certain embodiments, a smart carrier is disclosed that has a housingcomprising one or more docking locations configured to accept a securereceptacle, a wireless interface module disposed within the housing, anda processor disposed within the housing and operatively coupled to theone or more docking locations and the wireless interface module. Theprocessor is configured to communicate with an external device throughthe wireless interface module and with a secure receptacle that is matedwith one of the one or more docking locations. The smart carrier alsohas a battery disposed within the housing and configured to provide alloperational power to the processor, the wireless interface module, andthe one or more docking locations.

In certain embodiments, a system is disclosed that includes a securereceptacle having a body and a lib movable coupled to the body. The libhas a closed position that cooperates with the body to define acompartment. The receptacle also has a lib-securing actuator coupled tothe body and configured to engage the lib so as to secure the lib in theclosed position when not actuated and to release the lib when actuated.The receptacle also has a processor operatively coupled to thelib-securing actuator. The processor is configured to receive a messageand to selectably actuate the lib-securing actuator. The system alsoincludes a smart carrier having a housing comprising one or more dockinglocations configured to accept the secure receptacle, a wirelessinterface module disposed within the housing, and a processor disposedwithin the housing and operatively coupled to the one or more dockinglocations and the wireless interface module. The processor is configuredto communicate with an external device through the wireless interfacemodule and with the processor of a secure receptacle that is mated withone of the one or more docking locations. The smart carrier also has abattery disposed within the housing and configured to provide alloperational power to the processor, the wireless interface module, andthe one or more docking locations.

In certain embodiments, a method is disclosed that includes the steps ofmating a secure receptacle with a portable smart carrier therebyproviding power to the secure receptacle from a battery that is disposedwithin the smart carrier, the battery also providing all operationalpower to a wireless interface module and a carrier processor that iscoupled to the wireless interface module, scanning with a portable userinterface device (PUID) a first machine-readable identifier that isassociated with a medication, and identifying the mated securereceptacle by scanning with the PUID a second machine-readableidentifier disposed on the secure receptacle. The secure receptaclecomprises a memory containing a reference identifier and the secondmachine-readable identifier is associated with the reference identifierin a database. The method also includes the steps of associating themedication with the reference identifier and loading at least one doseof the medication into the secure receptacle.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide furtherunderstanding and are incorporated in and constitute a part of thisspecification, illustrate disclosed embodiments and together with thedescription serve to explain the principles of the disclosedembodiments. In the drawings:

FIG. 1. depicts an example dispensing system.

FIG. 2 depicts an open drawer of the ADM of FIG. 1 and the conventionalreceptacles contained therein.

FIG. 3 depicts an exemplary smart carrier according to certain aspectsof the present disclosure.

FIG. 4A depicts a plurality of exemplary secure receptacles attached toa smart carrier according to certain aspects of the present disclosure.

FIG. 4B depicts the corresponding features of another embodiment of asecure receptacle and another embodiment of a smart carrier according tocertain aspects of the present disclosure.

FIG. 4C is a partially exploded view of another secure receptacle 201according to certain aspects of the present disclosure.

FIG. 5 is a block diagram of an exemplary smart carrier according tocertain aspects of the present disclosure.

FIG. 6 is a schematic representation of an exemplary network accordingto certain aspects of the present disclosure.

FIG. 7 depicts an exemplary cart with a plurality of smart carriers andsecure receptacles according to certain aspects of the presentdisclosure.

FIG. 8 is a flow chart of an exemplary fill process according to certainaspects of the present disclosure.

FIG. 9 is a flow chart of an exemplary check process according tocertain aspects of the present disclosure.

FIG. 10 is a flow chart of an exemplary transport process according tocertain aspects of the present disclosure.

DETAILED DESCRIPTION

It is advantageous to provide a mobile carrier that provides power and acommunication link to secure receptacles such that the securereceptacles may be filled, checked, and operated at locations other thanfixed filling and dispensing systems.

The disclosed systems and methods of secure medication transportautomate the pick-check-delivery process to provide increased securityduring medication replenishment throughout a hospital as well as remotesite locations.

In the following detailed description, numerous specific details are setforth to provide a full understanding of the present disclosure. It willbe apparent, however, to one ordinarily skilled in the art thatembodiments of the present disclosure may be practiced without some ofthe specific details. In other instances, well-known structures andtechniques have not been shown in detail so as not to obscure thedisclosure. In the referenced drawings, like numbered elements are thesame or essentially similar. Reference numbers may have letter suffixesappended to indicate separate instances of a common element while beingreferred to generically by the same number without a suffix letter.

While the discussion herein is directed to the management of medicationsin a hospital, the disclosed concepts and methods may be applied toother fields that would also benefit from a secure method ofdistribution and dispensing. For example, valuable tools may be managedwith this system in a service facility.

Within this document, the term “battery” means energy storage devicesconventionally referred to as batteries, for example non-rechargeablecarbon batteries and rechargeable nickel-cadmium batteries, as well asall other types of portable power source, including but not limited toenergy storage devices, such as a capacitor, energy conversion devices,such as a photovoltaic cell, and energy generation devices, such as afuel cell, or combinations thereof.

Within this document, the phrases “portable user interface device” and“PUID” mean any mobile device that provides information and acceptsinput. A PUID may provide information via any channel including but notlimited to an optical display such as a light-emitting diode (LED)screen and an audible actuator such as a speaker or buzzer. A PUID mayaccept input via any channel including but not limited to an opticalscanner, a radio-frequency identification (RFID) reader includingelectric-field and magnetic-field systems, a keyboard, a touchscreen orstylus-activated screen, a microphone, and a joystick. PUIDs may includebut are not limited to tablet computers, laptop computers, desktopcomputers installed on a mobile platform, personal data assistants(PDAs), cellular phones, wirelessly connected devices such as iPods andiPads, and readers such as Kindle e-readers.

Within this document, the term “medication” comprises substances thatare conventionally considered to be medications, particularly substancesthat are available only by a doctor's prescription, as well as any othersubstance or mixture that may be used in a health-related treatment of apatient. Medications include but are not limited to medical fluids suchas a saline solution or Ringer's lactate, active compounds such as ananalgesic and an antimicrobial, and health-related substances such as avitamin.

Within this document, the term “scanning” means the input of amachine-readable feature and interpretation of the information encodedtherein. Scanning may include passive optical observation and recordingof a visual image, such as a barcode or 2D coded matrix, or may includeactive illumination, such as provision of a light beam that traverses aportion of the image, as is commonly done in a barcode scanner. Scanningmay also include provision of an energizing field, such as an electricfield or magnetic field as are commonly provided to read passive RFIDtags.

Within this document, the term “portable” means a size and weight thatis easily moved by an adult. While an object of any size and weight canbe moved, with the use of appropriate equipment, a portable device asconsidered herein would include devices of a size and weight that theywould not be burdensome to a person to keep with them for several hoursover the course of an 8-hour workday. Portable devices may be mounted ona rolling cart or other movable appliance, such as the wheeled computerplatforms commonly used in hospitals and known to those of skill in theart. Portable devices are not secured to a single location for extendedperiods of time during which the devices are used.

FIG. 1. depicts an example dispensing system 10. This system 10 includesan ADM 12 with a plurality of drawers 15 connected to an auxiliarycabinet 14 having a plurality of drawers 15 and a tall auxiliary cabinet16 with a plurality of doors 17 and shelves 18. In one mode ofoperation, the drawers 15 and doors 17 are secured such that thecontents are not available for removal. The ADM 12 includes a userinterface 13 and a processor (not visible in FIG. 1) that accepts inputfrom the user through the user interface 13. An example dispensingprocess would begin with a user identifying themselves to the ADM 12,for example by providing a login name and password through the userinterface 13. The ADM processor verifies that the identified user isauthorized to remove at least one item from the ADM 12, or attachedauxiliary cabinets 14 and 16, and activates an item-selection display.The user selects an item to be dispensed. The ADM processor verifiesthat the user is authorized to remove the selected item and unlocks thedrawer 15 or door 17 that contains the selected item. The user removesthe item, closes the drawer 15 or door 17, and logs out, whereupon theADM 12 locks the opened drawer 15 or door 17.

FIG. 2 depicts an open drawer 20 of the ADM 12 of FIG. 1 and theconventional receptacles 30 contained therein. The receptacles 30 are asdisclosed in the '461 patent and are marked with a label 32 that isprinted at the time of filling of the receptacle 30. The label 32includes text 34 that provides information regarding the medicationcontained in the receptacle 30, for example the medication name, dose,and expiration date. The label 32 also includes a barcode 36 that maycontain a portion of the same information or additional information,such as a tracking number associated with the latest filling of thisparticular receptacle 30. The receptacle 30 may also include anon-volatile memory (not visible in FIG. 2) that stores a uniqueidentification number associated with this receptacle 30. When thereceptacle 30 is plugged into the drawer 20, the ADM processor of theADM 12 can communicate with the memory of the receptacle 30 and retrievethe identification number associated with this receptacle 30. In somesystems, a central database (not shown in FIG. 2) contains a list ofidentification numbers and information regarding the contents of therespective receptacles 30 and the ADM 12 can communicate with thisdatabase to retrieve this information. Thus, plugging a receptacle 30into the drawer 20 informs the processor of the ADM 12 of the contentsof that receptacle 30.

FIG. 3 depicts an exemplary portable smart carrier 100 according tocertain aspects of the present disclosure. This embodiment of the smartcarrier 100 comprises a body 102 with a handle 104, a plurality ofdocking locations 106, a processor 120 (not visible in FIG. 3, shown inFIG. 5), and an external connector 108. In general, the smart carrier100 is sized to be portable and easily carried, for example by thehandle 104, and transported, for example on a cart. Each of the dockinglocations 106 comprises a connector 110, a retention feature 112, and anindicator 114. In certain embodiments, the connector 110 includeselectrical contacts (not visible in FIG. 3) that may provide one or moreof power, ground, and communication lines. In certain embodiments, theretention feature 112 comprises a detent element (not visible in FIG. 3)that retains a latching feature of a secure receptacle (not shown inFIG. 3) until the applied removal force exceeds a predetermined value.In certain embodiments, the retention feature 112 comprises a lockingelement (not visible in FIG. 3) that retains a latching feature of asecure receptacle (not shown in FIG. 3) until the locking element isunlocked by a command from the processor 120. In certain embodiments,the indicator 114 comprises a visual indicator, for example alight-emitting diode (LED). Additional features and capabilities of thesmart carrier 100 are discussed with respect to FIG. 5.

FIG. 4A depicts a plurality of exemplary secure receptacles 2××,referring generically to all configurations of secure receptacles thatmay come in various sizes, attached to a smart carrier 100 according tocertain aspects of the present disclosure. The example smart carrier 100of FIG. 3 has six docking locations 106, each configured to accept a“one wide” or “1×” secure receptacle 200, as shown in FIG. 4A wherein a1× secure receptacle 200 is docked in the third docking location 106from the handle 104.

Larger secure receptacles 2×× may occupy two or more adjacent dockinglocations 106. For example, a “two-wide” or “2×” secure receptacle 220is shown docked in the first and second docking locations 106.Similarly, a “three-wide” or “3×” secure receptacle 230 is shown dockedto the fourth, fifth, and sixth docking locations 106. In this example,the secure receptacle 230 is in operative contact only with the contact110 of the fifth docking location 106, as the contacts 110 of the fourthand sixth docking locations 106 are exposed with the secure receptacle230 in place. In certain embodiments, the secure receptacle 230 mayengage only the retention feature 112 of the fifth docking location 106,while in other embodiments the secure receptacle 230 may engage one orboth of the retention features 112 of the fourth and sixth dockinglocations 106.

FIG. 4B depicts the corresponding features of another embodiment of asecure receptacle 200 and another embodiment 100A of a smart carrieraccording to certain aspects of the present disclosure. Two 1× securereceptacles 200A and 200B are shown as docked in the first and seconddocking locations that are identical and are designated 106A and 106Bfor convenient specific identification. A third 1× secure receptacle200C is shown in an orientation that exposes the features that mate withelements of a docking location 106, and the specific docking location106D is used herein as an example of such. The secure receptacle 200Chas a body 213 with a pair of front feet 216 that include a shapedsurface 216-1 and a pair of rear feet 218. The rear feet 218 fit intothe pockets 118 and the front feet 216 fit into the recesses 116 whenthe secure receptacle 200C is mated with docking location 106D. In thisembodiment, the recesses 116 are formed such that one of the front feet216 of adjacent secure receptacles 2×× fit into a common recess 116while the pockets 118 are configured to accept individual rear feet 218.In other embodiments, the pockets 118 and recesses 116 may be providedin other configurations to accept single or multiple feet from one ormultiple secure receptacles.

There is an interface connector 210 that will mate with dockingconnector 110 when the secure receptacle 200C is docked with dockinglocation 106D. There is also a latching feature 212 on the body 213 thatengages a retention feature 112 of the smart carrier 100A. In certainembodiments, the interface connector 210 and docking connector 110 maybe replaced with a wireless communication link, for example inductivelycoupled plates, that allow communication and power to be transferredbetween the smart carrier 100 and secure receptacle 200 without directelectrical contact.

FIG. 4C is a partially exploded view of another secure receptacle 201according to certain aspects of the present disclosure. Securereceptacle 201 is a “half-height” version of the 1× “full height” securereceptacle 200 shown in FIGS. 4A and 4B, wherein the width and depth ofthe secure receptacles 200 and 201 are the same, and the features shownin FIG. 4B are common and identical for both, while the height of thesecure receptacle 201 is less than the height of the secure receptacle200. The lib 211 is movably coupled to the body 213 and, in certainembodiments, the lib 211 is hingedly attached to the body 213 at a backedge of the body 213. In certain embodiments, the lib 211 is the same ona half-height secure receptacle 201 and a full-height secure receptacle200 of the same width and depth.

A front cover has been removed from the body 213 to expose certaininternal elements, including a processor 219 and a lib-securing actuator217 that is configured to engage a latching feature such as the hook211-1 of the lib 211. In certain embodiments, the lib-securing actuator217 is configured to engage and retain the hook 211-1 so as to securethe lib 211 in a closed position, for example as shown by securereceptacle 200A in FIG. 4B. The processor 219 is operatively coupled tothe lib-retaining actuator 217 and the interface connector 110 (notvisible in FIG. 4C). When the lib 211 is closed, the lib 211 cooperateswith the body 213 to define a compartment 215. After the lib is closed,any items placed in the compartment 215 are secure until the securereceptacle 200 is docked with a receiving station such as a smartcarrier 100 and a command is received by the processor 219 through theinterface connector 210 to open the lib, whereupon the processoractuates the lib-retaining actuator 217 which releases the hook 211-1and allows the lib 211 to open. In certain embodiments, the securereceptacle 201 may comprise a biasing element, such as a spring, thaturges the lib 211 to move away from the closed position to an openposition such that the lib 211 will self-open upon release of the hook211-1 by the lib-securing actuator 217.

FIG. 5 is a block diagram of an exemplary smart carrier 100 according tocertain aspects of the present disclosure. There may be one or moredocking locations 106 in a smart carrier 100, wherein each dockinglocation 106 may have a connector 110, a retention feature 112, and anindicator 114. A processor 120 is operatively coupled to the connectors110 and the indicators 114. The processor 120 is also coupled to amemory 128, a wireless interface module 122, a wired interface module124, and an external connector 108.

In certain embodiments, the wireless interface 122 is configured tobidirectionally communicate with a wireless network (shown in FIG. 6),for example an 802.11 network, and communicate with an external device(shown in FIG. 6) through the network. In certain embodiments, the wiredinterface module 124 is configured to communicate with a wired network,for example an Ethernet network, through the external connector 108 andcommunicate with an external device through the network. The smartcarrier 100 also comprises a battery 126, or other portable powersource, that may be operatively coupled to the external connector 108,for example to accept recharging current, and provides all operationalpower to the elements of the smart carrier 100. In certain embodiments,the battery 126 may not be coupled to the external connector 108 andmust be periodically replaced. The battery 126 is operatively coupled toat least one of the processor 120, wireless interface module 122, wiredinterface module 123, connectors 110, and indicators 114, although theseconnections have been omitted in FIG. 5 for clarity as the distributionof power in an electronics system will be known to those of skill in theart.

In certain embodiments, the memory 128 is configured to store a carrieridentifier that is associated with the individual smart carrier 100.When a secure receptacle 2×× is docked with one of the docking locations106, the processor 120 may communicate with the processor 219 of thesecure receptacle 2×× and retrieve a reference identifier that isassociated with the individual secure receptacle 2××. The processor 120may then send the reference identifier of the secure receptacle 200 andthe carrier identifier to a server, though either the wired interfacemodule 124 or the wireless interface module 122, such that the serverknows that this particular secure receptacle 2×× is operatively dockedwith this particular smart carrier 100.

The processor 120 may also be configured to monitor the condition of thebattery 126, for example one or more of the current state of charge, theprovided voltage, the elapsed time since replacement, and the number ofrecharge cycles, and report one or more of these parameters to anexternal device.

Upon receipt of certain commands, for example a command to move a dockedsecure receptacle 200 from the smart carrier 100 to an ADM 12, theprocessor may activate an indicator 114 associated with one of thedocking locations 106.

FIG. 6 is a schematic representation of an exemplary network 240,270according to certain aspects of the present disclosure. There is aserver 260 located in a “hospital A” that is attached to a wired network270 and a wireless network 240 through an access point 250. A dispensingsystem 10A in the same building as the server 260 is also connected tothe wired network 270 and in communication with the server 260. Theserver 260 includes a memory (not visible in FIG. 6) that is configuredto store operating instructions and one or more databases. At least oneof the databases includes a listing of the reference identifiers thatare associated with secure receptacles 200 that are in use within thehospital A. This database or other databases may include a list ofpatients and their locations, which may be part of or related to an“admit-discharge-move” or “ADM” system, and a list of prescribedmedications.

Once a secure receptacle 200 is filled with a certain number of doses ofa medication, the database of the server 260 may store information aboutthe contents of the secure receptacle 200 in association with thereference identifier, which is the sole element of information stored inthe processor 219 of the secure receptacle 200, thereby treating thereference identifier similar to a “license plate” wherein the referenceidentifier does not contain any information about the contents of thesecure receptacle 200 but can be used to access this information in thedatabase of the server 260. In other embodiments, a copy of a portion ofthe information that is stored in the database of the server 260 may becopied into a memory of the processor 219 of the secure receptacle 200such that a recipient device, for example a dispensing system 10, mayretrieve the information about the contents of the secure receptacle 200from the processor 219 without a need to communicate with the sever 260.

FIG. 6 also shows a portable user interface device (PUID) 255 that maybe used in conjunction with the smart carrier 100. Example processes areshown in FIGS. 8-10. The PUID 255, shown in FIG. 6 as a stylus-activatedtablet, may be wirelessly connected through the wireless network 240 andaccess point 250 to the server 260 and can provide input from the useras well as receive and display information sent from by the server 260to the PUID 255. The PUID 255 may include the ability to scan andinterpret machine-readable identifiers, for example a barcode or 2Dcode, as may be used to identify a medication or a device. In certainembodiments, the PUID 255 does not interact directly with a smartcarrier 100. In other embodiments, a PUID 255 be provided with areference identifier of a smart carrier 100, for example by scanning acarrier identifier that is available as a barcode attached to the smartcarrier 100 and sending this scanned carrier identifier to the server260, which responds with the reference identifier associated with thescanned carrier identifier and thereby enables the PUID 255 to interactdirectly with the smart carrier 100. In other embodiments, a PUID 255may be linked to a local smart carrier 100 through a process similar topairing of Bluetooth® devices as is known to those of skill in the art.

The server 260 may also be connected to dispensing system 10B located inanother building, for example a hospital “B.” The wired network 271 thatconnects to the other building may include a dedicated line, such as aT1 line, between hospitals A and B or an intermittent connection, forexample through the internet.

For an example of an order to deliver a medication to a specificdispensing system 10, the server 260 can exchange information with thePUID 255 as part of the filling process 300, discussed in greater detailwith respect to FIG. 8, and then provide the destination dispensingsystem 10 with information related to the secure receptacle 200 thatcontains the medication to be delivered to that dispensing system 10.

FIG. 7 depicts an exemplary cart 290 with a plurality of smart carriers100 and secure receptacles 200 according to certain aspects of thepresent disclosure. As the smart carriers 100 are portable andself-contained, i.e. can function while separated from any source ofpower, a cart 290 is a convenient way to carry and use multiple smartcarriers 100. In certain embodiments, the cart 290 may be configured topass through stock shelves within a pharmacy so as to enable a pharmacytechnician to fill secure receptacles 200 at the storage location of amedication, rather than having to carry multiple doses of the medicationto a fixed filling station within the pharmacy. In certain embodiments,the cart may be configured to transfer the secure receptacles 2×× fromthe pharmacy to one or more dispensing systems, for example thedispensing system 10 of FIG. 1. In certain embodiments, the cart 290 maycomprise storage features such as drawers, storages compartments withdoors, or other storage arrangements as will be known to those of skillin the art. In certain embodiments, one or more of these storagefeatures may be lockable as will be known to those of skill in the art,thereby providing secure storage during transport.

FIG. 8 is a flow chart of an exemplary fill process 300 according tocertain aspects of the present disclosure. The process will be describedwith reference to the smart carrier 100 and secure receptacle 200 forconvenience, although it will apparent to those of skill in the art howsimilar processes may be accomplished with alternate embodiments ofeither device. The process starts at step 305 when a user, for example apharmacy technician, docks a secure receptacle 200 with one of thedocking locations 106 of a secure carrier 100. The processor 120 of thesmart carrier 100 establishes communication with the processor 219 ofthe secure receptacle 200 and retrieves a reference identifier from theprocessor 219. The processor 120 sends this reference identifier to aserver 260. The user then uses a PUID 255 in step 310 to scan amachine-readable medication identifier, for example a barcode, that isassociated with a medication, for example printed on a container of themedication. The user then uses the PUID 255 in step 315 to scan amachine-readable receptacle identifier, for example a barcode, that isassociated with the docked secure receptacle 200, for example printed onthe lib 112 of the secure receptacle 200. The PUID 255 provides themedication and receptacle identifiers to the server 260, which comparesthe receptacle identifier to a list of associated reference identifiersand receptacle identifiers, for example a list contained in a databasestored in a memory attached to the server 260. The server 260 determinesthe reference identifier that is associated with the provided receptacleidentifier and creates a fill record in the database that the identifiedsecure receptacle 200 that is associated with the provided receptacleidentifier is being filled with the medication associated with theprovided medication identifier.

As part of step 315, the server 260 sends a “lib open” command to theprocessor 120 to open the lib 112 of the docked secure receptacle 200.The processor 120 sends a command to the processor 219 to open the lib112, and the processor 219 actuates the lib-securing actuator 217,thereby releasing the lib 112 that, in this example, self-opens underthe urging of a spring. The user proceeds to step 320 and transfers adetermined quantity of the medication into the compartment 215 of thesecure receptacle 200, inputs the quantity transferred into the PUID 255in step 325 and optionally enters additional information, for example anexpiration date, in step 330. The PUID 255 sends this information to theserver 260, which updates the previously created fill record. The userthen closes the lib 112 in step 335, whereupon the processor 219 sends asignal to the processor 120 that the lib 112 is closed. The processor120 forwards this information to the server 260, which closes the fillrecord as complete, thereby completing the fill process 300.

FIG. 9 is a flow chart of an exemplary check process 400 according tocertain aspects of the present disclosure. For this example, it ispresumed that the check process 400 follows the fill process 300 andthat the secure receptacle 200 is still attached to the smart carrier100. The process starts at step 405 when a user, for example a licensedpharmacist, uses the PUID 255 to scan the machine-readable receptacleidentifier on the docked secure receptacle 200. The PUID 255 sends thereceptacle identifier to the server 260, which retrieves the fill recordand sends this information to the PUID 255, which displays thisinformation in step 410. If the user wishes to open the lib 112 todirectly inspect the medications in the compartment 215, the user mayoptionally input a command into the PUID in step 415 to open the lib112, whereupon the PUID 255 send the request to the server 260 thatsends a “lib open” to the processor 120, in turn sends a command to theprocessor 219 to open the lib 112, and the processor 219 actuates thelib-securing actuator 217, thereby releasing the lib 112 in step 417.After the user verifies in step 420 that the secure receptacle 200contains the proper quantity of the proper medication, and optionallyother information, the user inputs an approval on the PUID 255 in step425, whereupon the PUID 255 sends the approval to the server 260 whichannotates the fill record to indicate that the fill was checked andapproved. If the lib 112 was opened, the process branches at decisionpoint 430 and the user closes the lib 112 in step 432, therebycompleting the check process 400.

FIG. 10 is a flow chart of an exemplary transport process 500 accordingto certain aspects of the present disclosure. For this example, it ispresumed that the transport process 500 follows the check process 400and that the secure receptacle 200 is still attached to the smartcarrier 100. The process starts at step 505 when a user, for example apharmacy technician, picks up a smart carrier 100 with a securereceptacle 200 docked in one of the docking locations 106. If thedestination of the secure receptacle 200 is a dispensing system 10within the same building, the process 500 branches to step 510 whereinthe user places the smart carrier 100 on a cart 290 such as shown inFIG. 7. In certain embodiments, the destination of a filled securereceptacle 200 may be any of a refrigerated cabinet, a beside storagecompartment in a patient's room, an infusion pump or other medicaldevice, or a designated storage location, for example a locked inventoryarea. The user moves the cart 290 to the location of the dispensingsystem 10 in step 515 and scans a machine-readable dispenser identifier,for example a barcode, on the dispensing system 10 with the PUID 255.The PUID 255 sends this dispenser identifier to the server 260,determines which medications are intended to be loaded into thisdispensing system 10, and then determines which secure receptacles 200contain these medications and the reference identifiers of thosereceptacles 200.

For this example, a single medication is intended to be delivered tothis dispensing system 10 and the server 260 sends the referenceidentifier to the processor 120 of the smart carrier 100 to which thedetermined secure receptacle 20 is docked. In step 525, the processor120 activates the indicator 114 that is associated with the dockinglocation 106 to which the determined secure receptacle 200 is docked. Instep 530, the user removes the secure receptacle from the dockinglocation 106 having the activated indicator 114 and, in step 535, docksthe removed secure receptacle 200 with the dispensing system 10, thusterminating the transport process 500 for this secure receptacle 200.Step 535 may include additional activities to log into the dispensingsystem 10 and open the storage location, for example a drawer, prior todocking the secure receptacle 200. The user may then repeat steps515-535 to deliver other secure receptacles 200 to other dispensingsystems 10 in the same building.

If, in step 505, the user determines that the secure carrier 100 hassecure receptacles 200 that are to be delivered to a dispensing system10 in another building, for example a hospital “B” as shown in FIG. 6,that is part of a group of hospitals, then the process 500 branches tostep 540 and the user places the smart carrier 100 in a tote or othertransport container. The user places the tote in a vehicle, for examplea van, in step 545 and a driver, which may be the same user or adifferent person, moves the vehicle to the destination building, e.g.the other hospital, in step 550. In step 555, the driver, or anotheruser such as a pharmacy technician, transfers the smart carrier 100 fromthe tote to a cart 290. This branch of process 500 then follows thesteps 515-535 within this second building to complete the process.

It can be seen that the disclosed embodiments of the smart carrier, inconjunction with secure receptacles and a mobile input device, allow apharmacist to dispense and transport medication with greater ease andimproved safety but allowing them to move the disclosed systems to thelocation of the medications, or other convenient work locations, and notbe limited by a fixed location, for example a filling station located ina fixed location in a pharmacy. The linkage of the various disclosedsystems also provides improved record-keeping as the information isimmediately provided to and stored by a central server.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. While theforegoing has described what are considered to be the best mode and/orother examples, it is understood that various modifications to theseaspects will be readily apparent to those skilled in the art, and thegeneric principles defined herein may be applied to other aspects. Thus,the claims are not intended to be limited to the aspects shown herein,but is to be accorded the full scope consistent with the languageclaims, wherein reference to an element in the singular is not intendedto mean “one and only one” unless specifically so stated, but rather“one or more.” Unless specifically stated otherwise, the terms “a set”and “some” refer to one or more. Pronouns in the masculine (e.g., his)include the feminine and neuter gender (e.g., her and its) and viceversa. Headings and subheadings, if any, are used for convenience onlyand do not limit the invention.

To the extent that the terms “include,” “have,” or the like are used inthe description or the claims, such terms are intended to be inclusivein a manner similar to the term “comprise” as “comprise” is interpretedwhen employed as a transitional word in a claim.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an illustration of exemplary approaches. Basedupon design preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged. Some of the stepsmay be performed simultaneously. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

Terms such as “top,” “bottom,” “front,” “rear” and the like as used inthis disclosure should be understood as referring to an arbitrary frameof reference, rather than to the ordinary gravitational frame ofreference. Thus, a top surface, a bottom surface, a front surface, and arear surface may extend upwardly, downwardly, diagonally, orhorizontally in a gravitational frame of reference.

A phrase such as an “aspect” does not imply that such aspect isessential to the subject technology or that such aspect applies to allconfigurations of the subject technology. A disclosure relating to anaspect may apply to all configurations, or one or more configurations. Aphrase such as an aspect may refer to one or more aspects and viceversa. A phrase such as an “embodiment” does not imply that suchembodiment is essential to the subject technology or that suchembodiment applies to all configurations of the subject technology. Adisclosure relating to an embodiment may apply to all embodiments, orone or more embodiments. A phrase such an embodiment may refer to one ormore embodiments and vice versa.

The word “exemplary” is used herein to mean “serving as an example orillustration.” Any aspect or design described herein as “exemplary” isnot necessarily to be construed as preferred or advantageous over otheraspects or designs.

No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using thephrase “means for” or, in the case of a method claim, the element isrecited using the phrase “step for.”

What is claimed is:
 1. A portable carrier comprising: a housingincluding a docking location, wherein the docking location includes aretention feature formed to engage with a secure receptacle, the housingconfigured to be removably coupled to a cart, wherein the cart isconfigured to couple with a plurality of portable carriers; an indicatorassociated with the docking location; a wireless interface moduledisposed within the housing; a processor disposed within the housing andoperatively coupled to the docking location and the wireless interfacemodule; an energy storage device disposed within the housing, the energystorage device electrically coupled with the processor, the wirelessinterface module, and the docking location to provide operational power;and wherein the docking location further includes a connectorelectrically coupled with the energy storage device and arranged totransmit power to the secure receptacle at the docking location, whereinthe processor is configured to: activate the indicator when the dockinglocation receives the secure receptacle; receive, via the wirelessinterface, a command to adjust the secure receptacle; and cause thesecure receptacle to perform an adjustment corresponding to the command.2. The portable carrier of claim 1, wherein the command includes a firstidentifier and wherein the processor is configured to: retrieve a secondidentifier from a the secure receptacle that is mated with the dockinglocation; and cause the secure receptacle to perform the adjustmentafter determining that the first identifier matches the secondidentifier.
 3. The portable carrier of claim 1, wherein: the securereceptacle comprises a body, a lib having a closed position thatcooperates with the body to form a compartment, and a lib actuatoroperatively coupled to the processor, the lib actuator configured toengage the lib when not actuated so as to retain the lib in the closedposition and to release the lib when actuated, thereby allowing the libto open; and wherein the adjustment includes actuating the lib actuator.4. The portable carrier of claim 1, wherein: the secure receptaclecomprises a processor coupled to an interface connector; and theprocessor of the portable carrier is in two-way communication with theprocessor of the secure receptacle through the interface connector andthe connector.
 5. The portable carrier of claim 1, further comprising amemory comprising instructions, wherein the processor is configured toretrieve the instructions from the memory and execute the instructions.6. The portable carrier of claim 1, wherein the processor is furtherconfigured to transmit a command to the secure receptacle to release asecurable lib that is movably coupled to a body of the secure receptacleand cooperates with the body to define a compartment within the securereceptacle when the securable lib is in a closed position, therebyallowing access to the compartment, and a dose of a medication in thecompartment.
 7. The portable carrier of claim 1, wherein the processoris configured to cause the receptacle to perform the adjustment by atleast: transmitting the command to a docking connector that is coupledwith the processor and therethrough to a mated interface connector ofthe secure receptacle to retain a lib of the secure receptacle in aclosed position when not actuated and to release the lib when actuated,thereby allowing the lib to open.
 8. The portable carrier of claim 1,wherein the wireless interface module is communicatively coupled to aserver and wherein the processor is configured to: monitor a state ofthe energy storage device; and transmit, via the wireless interfacemodule to the server, a message reporting the state.
 9. The portablecarrier of claim 8, wherein the wireless interface module is configuredto: provide an identifier for the secure receptacle to the server;retrieve a reference identifier from a database; and access a record inthe database and associate a medication with the reference identifier.10. The portable carrier of claim 1, wherein the processor is furtherconfigured to: close a lib to secure a dose of a medication in thesecure receptacle; and transmit a message to update a record in adatabase to indicate that a fill process for the secure receptacle iscomplete.
 11. A system, comprising: a secure receptacle comprising: abody; a lib movably coupled to the body, the lib having a closedposition that cooperates with the body to form a compartment; and a libactuator configured to engage the lib when not actuated so as to retainthe lib in the closed position and to release the lib when actuated,thereby allowing the lib to open; and a portable carrier comprising: ahousing including a docking location, wherein the docking locationincludes a retention feature formed to engage with the securereceptacle, the housing configured to be removably coupled to a cart,wherein the cart is configured to couple with a plurality of portablecarriers; an indicator associated with the docking location; a wirelessinterface module disposed within the housing; a processor disposedwithin the housing and operatively coupled to the docking location, thelib actuator and the wireless interface module; and wherein the dockinglocation further includes a connector arranged to transmit power to thesecure receptacle at the docking location, wherein the processor isconfigured to: activate the indicator when the docking location receivesthe secure receptacle; receive, via the wireless interface, a command toadjust the secure receptacle; and cause the secure receptacle to performan adjustment corresponding to the command.
 12. The system of claim 11,wherein the command includes a first identifier and wherein theprocessor is configured to: retrieve a second identifier from the securereceptacle that is mated with the docking location; and cause the securereceptacle to perform the adjustment after determining that the firstidentifier matches the second identifier.
 13. The system of claim 11,wherein the adjustment includes actuating the lib actuator.
 14. Thesystem of claim 12, wherein the processor comprises a memory configuredto store the first identifier.
 15. The system of claim 12, furthercomprising a portable user interface device configured to scanmachine-readable identifiers, wherein the secure receptacle comprises amachine-readable feature comprising a third identifier that isassociated with the first identifier.
 16. The system of claim 11,wherein the portable carrier further comprises a memory comprisinginstructions, wherein the processor is configured to retrieve theinstructions from the memory and execute the instructions.
 17. Thesystem of claim 11, wherein: the secure receptacle comprises a processorcoupled to an interface connector; and the processor of the portablecarrier is in two-way communication with the processor of the securereceptacle through the interface connector and the connector.
 18. Thesystem of claim 11, wherein the processor is further configured to:update a record in a database to indicate that the compartment isfilled; scan with the wireless interface module a machine-readableidentifier disposed on the secure receptacle; retrieve, from a record inthe database, information related to a medication in the securereceptacle and display the information on a display; verify that themedication in the secure receptacle matches the record in the database;and update the record in the database to indicate that a check processis complete.
 19. The system of claim 12, wherein the processor isfurther configured to: scan with the wireless interface module a thirdidentifier that is associated with a dispensing system; retrieve, from adatabase, a reference identifier of the secure receptacle that containsa medication intended to be delivered to the dispensing system that isassociated with the third identifier; and activate an indicatorassociated with the docking location in which the secure receptacle isdocked.
 20. The system of claim 19, wherein the processor is furtherconfigured to: remove the secure receptacle from the docking locationassociated with the indicator; dock the secure receptacle; and update arecord that a transport process is complete.